<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'Short Twitter handles are no longer available',
	'body' => <<<END
<p>
	I changed my Twitter handle, looking for something shorter.
	Along the way, I found that the nick <code>YstS</code> was not taken, but in trying to switch to it, I found that Twitter disallows handles as short as four characters.
	Any account with a handle shorter than fivecharacters must have been grandfathered from a time before this rule.
	Though the <code>Yst</code> account exists, I can never aquire that name, even if the current holder of that nick deletes his or her account.
	I am now using one of the shortest handles still available to me: <code>YstDo</code>.
</p>
<p>
	The <a href="https://bynumlaw.net/">Bynum Law office</a>, home of a Texan criminal defense attorney, has set up their own <a href="http://tor-exit.bynumlaw.net/">$a[Tor] exit node</a> with a powerful message attached.
	Visiting the exit node&apos;s server over $a[HTTP], you see a page explaining that he knows his rights and will not be intimidated into taking down the server, &quot;intellectual property&quot; be damned.
	My paraphrasing really doesn&apos;t do the statement justice, so you should head over and take a look yourself if you are interested.
</p>
<p>
	<a href="https://sideshowbarker.net/">Mike</a> says that the reason that the $a[W3C] validator has been failing so badly on my site is that said validator is not $a[SNI]-compatible.
	As soon as I enabled $a[SNI] on my server, my site was doomed to be unable to be reached by legacy clients that do not have this support.
	I asked him about what I need to do to restore this compatibility, but he said that restoring compatibility with legacy clients was not the answer.
	Rather, I should avoid using such outdated clients, such as the old well-known $a[W3C] validator, and instead use the new $a[W3C] validator that he recommended before.
	I suppose that means my work on this matter is complete, as I already updated all the links across the site to point to the new validator the first time he brought it to my attention.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
